Ingrese una palabra o frase en cualquier idioma 👆
Idioma:
Traducción y análisis de palabras por inteligencia artificial ChatGPT
En esta página puede obtener un análisis detallado de una palabra o frase, producido utilizando la mejor tecnología de inteligencia artificial hasta la fecha:
- cómo se usa la palabra
- frecuencia de uso
- se utiliza con más frecuencia en el habla oral o escrita
- opciones de traducción
- ejemplos de uso (varias frases con traducción)
- etimología
Qué (quién) es 4 1 architectural view model - definición
VIEW MODEL IN SOFTWARE ARCHITECTURE
4+1; 4+1 View Model; 4+1 Architectural View Model
4+1 architectural view model
4+1 is a view model used for "describing the architecture of software-intensive systems, based on the use of multiple, concurrent views".Kruchten, Philippe (1995, November).
Model–view–controller
SOFTWARE ARCHITECTURAL PATTERN FOR USER INTERFACES WHICH DIVIDES THE RELATED PROGRAM LOGIC INTO THREE INTERCONNECTED ELEMENTS TO SEPARATE INTERNAL REPRESENTATIONS OF INFORMATION AND HOW INFORMATION IS PRESENTED TO AND ACCEPTED FROM THE USER
Model view controller triad; Model view controller; Model/View/Controller; Model-View-Controller; Model View Controller; MVC Design Pattern; Model-view-controller design pattern; MVC model; MVC Pattern; Model-view; Model-Template-View; Model-view controller; Model-view-controller; MVC architecture; Model–View–Controller; Model-view-controller/; Model-View-Controller paradigm; Model, view, controller; MVC view; MVC controller; Model (MVC); View (MVC); Controller (MVC); Model-template-view
Model–view–controller (MVC) is a software architectural pattern commonly used for developing user interfaces that divide the related program logic into three interconnected elements. This is done to separate internal representations of information from the ways information is presented to and accepted from the user.
Model View Controller
SOFTWARE ARCHITECTURAL PATTERN FOR USER INTERFACES WHICH DIVIDES THE RELATED PROGRAM LOGIC INTO THREE INTERCONNECTED ELEMENTS TO SEPARATE INTERNAL REPRESENTATIONS OF INFORMATION AND HOW INFORMATION IS PRESENTED TO AND ACCEPTED FROM THE USER
Model view controller triad; Model view controller; Model/View/Controller; Model-View-Controller; Model View Controller; MVC Design Pattern; Model-view-controller design pattern; MVC model; MVC Pattern; Model-view; Model-Template-View; Model-view controller; Model-view-controller; MVC architecture; Model–View–Controller; Model-view-controller/; Model-View-Controller paradigm; Model, view, controller; MVC view; MVC controller; Model (MVC); View (MVC); Controller (MVC); Model-template-view
<programming> (MVC) A way of partitioning the design of
interactive software. The "model" is the internal
workings of the program (the algorithms), the "view" is how
the user sees the state of the model and the "controller" is
how the user changes the state or provides input.
(2007-05-30)
Wikipedia
4+1 architectural view model
4+1 is a view model used for "describing the architecture of software-intensive systems, based on the use of multiple, concurrent views". The views are used to describe the system from the viewpoint of different stakeholders, such as end-users, developers, system engineers, and project managers. The four views of the model are logical, development, process and physical view. In addition, selected use cases or scenarios are used to illustrate the architecture serving as the 'plus one' view. Hence, the model contains 4+1 views:
- Logical view: The logical view is concerned with the functionality that the system provides to end-users. UML diagrams are used to represent the logical view, and include class diagrams, and state diagrams.
- Process view: The process view deals with the dynamic aspects of the system, explains the system processes and how they communicate, and focuses on the run time behavior of the system. The process view addresses concurrency, distribution, integrator, performance, and scalability, etc. UML diagrams to represent process view include the sequence diagram, communication diagram, activity diagram.
- Development view: The development view illustrates a system from a programmer's perspective and is concerned with software management. This view is also known as the implementation view. UML Diagrams used to represent the development view include the Package diagram and the Component diagram.
- Physical view: The physical view (aka the deployment view) depicts the system from a system engineer's point of view. It is concerned with the topology of software components on the physical layer as well as the physical connections between these components. UML diagrams used to represent the physical view include the deployment diagram.
- Scenarios: The description of an architecture is illustrated using a small set of use cases, or scenarios, which become a fifth view. The scenarios describe sequences of interactions between objects and between processes. They are used to identify architectural elements and to illustrate and validate the architecture design. They also serve as a starting point for tests of an architecture prototype. This view is also known as the use case view.
The 4+1 view model is generic and is not restricted to any notation, tool or design method. Quoting Kruchten,
The “4+1” view model is rather “generic”: other notations and tools can be used, other design methods can be used, especially for the logical and process decompositions, but we have indicated the ones we have used with success.
